Hybrid Model

Since Orchestra has to solve different requirements that are opposite to each other, a very flexible approach is required that can fit to all of this requirements. Therefore the idea of hybrid processing model was created. This hybrid process model tries to serves the two ares of interfaces scenario to its best

High performance with synchronous, service-oriented interfaces

• Message storing in main memory

• No overhead due to multiple parsing

• No overhead due to storing of states

Secure, reliable and robust with asynchronous processing

• Persistent storage of messages

• Efficient message access through optimized storage structure

• Maintaining of processing state in the database

• No message size limitation

• Resilient against errors caused by integrated restart

A special case of the persistent mode are so called mass data messages. Mass data messages have to be used when Orchestra has to process very huge messages. This special mode stores a message not as one big block, but in small pieces of 4 mega byte into the database. This is important when messages are transferred and read. When ever a message is read, not the whole messages is read into memory, the message is processed block wise. For a developer this is transparent. Orchestra presents a mass data message in the same way to the user than a volatile or normal persistent message. Internally a paged mechanism is working.